Version: $id$
group PICS_UsageStatement_FrontEnd {
// PICS_UsageStatement_FrontEnd parameters.
modulepar {
boolean PIC_usageStatementID : = true ; boolean PIC_regimeID : = true ; boolean PIC_aggregatedFee : = true ; boolean PIC_vat : = true ; boolean PIC_aggregatedSingleTariffClassSession : = true ; boolean PIC_listOfDSRCUsageData : = true ; boolean PIC_listOfRawUsageData : = true ; boolean PIC_additionalUsageInformation : = true ; boolean PIC_usageAuthenticator : = true ;
}
}|
Generated with T3Doc 2.0 on Thu Jan 06 00:06:01 CET 2011.
Description
Does the EUT implement reportRecipientId field? Does the EUT implement dataReceived field? Does the EUT implement versionsResponse field? Does the EUT implement obeStatusForDriver field? Does the EUT implement accountUpdate field? Does the EUT implement responseAuthenticator field? Electronic fee collection (EFC) — Conformity evaluation of Front End and Back End equipment to ISO 17575-1 — Part 1: Test suite structure and test purpose - Annex B.3: Optinal data elements
Remarks
PICS Reference: Annex B.3.2: ChargeReportResponse